Originally by: Keiko Kobayashi

---

Authentication

The EVE API does not use standard HTTP authentication. Instead, it passes the authentication information via POST parameters. It is however better to use the built-in HTTP authentication functionality, primarily because many HTTP applications and stacks have built-in support for it.

---

Quote:

---

Pretty URLs

Part of REST is good URL design. This is actually not really really important, but it's one of the things that is usually the first things that people notice.

---

Originally by: Mantalari Altis

---

[if someone give me his ApiKey] I can even check to see what other characters they have on the same account and see corp membership of each character [...]

---

Quote:

---

/char/<characterID>/charactersheet
/char/<characterID>/accountbalance
/char/<characterID>/walletjournal
/char/<characterID>/walletjournal/<accountKey>
/char/<characterID>/walletjournal/<accountKey>/<beforeRefID>
/char/<characterID>/wallettransactions
/char/<characterID>/wallettransactions/<accountKey>
/char/<characterID>/wallettransactions/<accountKey>/<beforeRefID>

---

Originally by: Tonto Auri

---

Access Control based on pretty URL's

...

At first, let's look at subtrees. We clearly see one way to improve scalability and reduce number of subtrees. Sheme may be:

/char/<characterID> <- special meaning
/char/<characterID>/charactersheet <- skills
/char/<characterID>/charactersheet/skillTraining <- skill currently in training
/char/<characterID>/wallet <- balance
/char/<characterID>/wallet/journal
/char/<characterID>/wallet/journal/<beforeRefID>
/char/<characterID>/wallet/transactions
/char/<characterID>/wallet/transactions/<beforeRefID>

(I remove accountKeyId as unusual for personal wallet)

After that, we may have one main apiKey for whole /char/<characterID>/* tree and 2 restricted subkeys - to access charactersheet and wallet.

---

Originally by: Amida Ta

---

Is there any specific reason why to not make this a web-service
This is cool as hell already, but as web-service it would be even better

/me is for web-service

---

Originally by: Amida Ta

---

Then where are the WSDL-Files?
Moreover the output doesn't look very Web-Service like.
And the input seems to be a normal HTTP post. No Web-Service style either (at least not using SOAP)...

---

Originally by: DevAmarr Null

---

Hello everyone,

I am looking at this API, but didn't see how can one get characterID easily. As till now, you can get it manually checking the links under My Character section, but that's kind of not good. It would be easier if we would have some sort og XML/CSV that would give back all charatersID connected to userID and API key. Or am I just missing that information?

cu

---

Originally by: 45thTiger 002

---

The main useabililty issue is directing users wanting to provide the data for a corp web site, or a site that generates sig blocks, is that a lot of players have no idea what the character id they wish to use actually is.

The way its implemented now, you need to direct them to two / three places to do it for dumb users.
1st to the API Key page and then to a custom IGB site to get the active character id.

---

Quote:

---

And even then, to link them into a clan portal you'd need to re-auth them against user id on the portal site and the portal may or may not work in the IGB.

---

Quote:

---

It would be preferable if the API Key page at least provided a list of characters on the account and the associated character IDs for the user to cut and paste.

---

Quote:

---

Even simpler would be to expose the userid and apikey to the IGB when a user trusts a site. (Yeah yeah I know!)

---

Quote:

---

Regarding corp wallet access, I would suggest that the API Key site once again be upgraded to generate a corpid / apikey for users with director role. Accessing corp data through user is dangerouse as mentioned earlier.

---

Quote:

---

Regarding re-requesting transaction history, to reduce load it would be best to allow a parameter that specified the max record to retreive, otherwise each call will fetch 1000 rows, only a few of them may be applicable depending on activity.

---

Quote:

---

That being said, the API is an excellent step forward for EVE and the EVE Community. (Maybe one day it will accept data so corp management can be done on the portal and the changes fed back to Eve - HAHAHHA!

---

Originally by: Ovno ConSyquence

---

does anyone know if this data will be availble through the myeve web interface as well or am i going to have to write some code just to get hold of my wallet exports in csv?

---

Originally by: Crescend

---

Hangar dump, with basic item stats for each item (especially BPCs) and numbers of each item would be very, very appreciated. As is, managing multiple major factory locations and keeping track of multiple R&D and supply chains is a gigantic hassle.

---

Originally by: CCP Garthagk

---

After some discussion, we've decided to slightly change the way the API keys work. Notably, there will be two keys going forward: a low security one and a high security one.

---

Originally by: FlashFF

---

I honestly dont see that the RESTful model is massively important. In fact, given the choice I'd personally go without it.

---

Originally by: Amida Ta

---

HTTPS is probably not a good idea to use. With the supposed usage model (LOTS of atomic calls) it would put gigantic stress onto the server.

---

Originally by: Neonemesis

---

jeez u dont need <?php, <? will do it is exactly the same^^

---

Quote:

---

php_flag short_open_tagOff

---

Originally by: Ashoka TG

---

Why is it that I can access my wallet only once every so many minutes? Moreover, why isn't this limit documented anywhere.

---

Quote:

---

Secondly, is a market export coming? I don't mind CCP saying no, I just want an answer, we've all been waiting too long.

---

Originally by: TornSoul

---

I only wish the 1 hour cache was per char, and not per account.

Pulling all wallets from 3 chars, you have to wait an hour betweeen each...

Could we please have this changed to a per char basis.

---

Originally by: Ray McCormack

---

Tbh, it's not the i-win button for traders everyone thinks it will be. It will simply be another tool in this great dynamic that is the EVE market. It will give no advantage that it doesn't counter-measure in itself.

---

Originally by: Jaabaa

---

2) The characters list.

The characters on an account "/account/Characters.xml.aspx" should only be accessible with the full key. It might even be a better idea to have a limited key per character, so that people can't guess at (and confirm) your alts on an account.

---

Quote:

---

<?php

$auth = array(
'userID' => 'nnnnnn',
'apiKey' => 'insertapikeyoverhere',
'characterID' => 'nnnnnnn'
);

$api_url = 'http://api.eve-online.com/corp/MemberTracking.csv.aspx';

?>

---

Quote:

---

<?php

$ch = curl_init($api_url);

curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);

$_req = '';
foreach($auth as $key => $value)
{
$_req .= (strlen($_req) ? '&' : '') . urlencode($key) . '=' . urlencode($value);
}

curl_setopt($ch, CURLOPT_POSTFIELDS, $_req);

$rc = curl_exec($ch);

?>

---

Quote:

---

<?php

require_once('Net/Curl.php');

$ch = new Net_Curl();
$ch->url = $api_url;
$ch->fields = $auth;

$rc = $ch->execute();

?>

---

Quote:

---

<pre>
<?php

print(htmlspecialchars($rc));

?>
</pre>

---

Originally by: DeTox MinRohim

---

Because CURL is not necessarily enabled on every hosts

---

Quote:

---

<?php

$ch = curl_init($api_url);

curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($auth));

$rc = curl_exec($ch);

?>

---

Originally by: Luf Yu'Wong

---

<?php
file_get_contents($path);
?>

This should be faster if using PHP 5 as it uses streams.

---

Quote:

---

And since we are getting an XML document then we have no issues in getting everything.

---

Originally by: Jalf

---

Could just be something like the following:
<error code="101">Wallet exhausted: retry after <time>2007-07-26 22:34:07</time></error>

---

Originally by: Iachrites Archveult

---

The thing to notice here is that the skillpoints count is correct. 633568 is right for level 4. Yet the API says the level is 3.

Seems to be some kind of error in the API at some level.

---

Originally by: Iachrites Archveult

---

IA

---

Originally by: Lord Choronic

---

I'm sorry. but I still have no clue on how to get a hold of the information :( I'm seriously a noob when it comes to Internet Explorer and that jazz, help would be appriciated

---

Originally by: Vulcar Dumas

---

Why is this not working, it outputs a blank page-

<?php
$data = array(
'userID' => "xxx",
'apiKey' => "xxxx"
);

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, "http://api.eve-online.com/char/WalletJournal.xml.aspx");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $data);

---